3D mapping of a process control environment

ABSTRACT

In a method of mapping a real-world process control environment, a mobile device is registered at a reference location, and 3D positions and orientations of the mobile device are tracked using an inertial measurement unit. A user input indicating that a new node is to be added to a 3D map of the process control environment is detected, and a 3D position of a real-world object relative to the reference location is determined, or caused to be determined, based on a tracked 3D position and orientation of the mobile device. A node database is caused to add the new node to the 3D map of the process control environment, at least by causing the 3D position of the real-world object to be stored in association with the new node.

CROSS-REFERENCE TO RELATED APPLICATIONS

This claims the benefit of U.S. Provisional Patent Application No. 62/564,074, filed on Sep. 27, 2017 and entitled “Augmented Reality Platform,” the disclosure of which is hereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to augmented reality technology, and, more particularly, to an augmented reality platform that may be utilized in process control or other environments.

BACKGROUND

Augmented reality (AR) systems that provide for the overlay of digital information (e.g., text, images, animation, etc.) on real-world environments, are becoming increasingly common as new applications for the technology are explored. AR systems typically provide information that is specific to the context of the user's current real-world surroundings. For such systems, real-world knowledge is generally required, such as knowledge of physical things that are currently in a user's view, and the physical layout at and around the current location of the user. To make this sort of information available to the AR system, a three-dimensional (3D) digital model representing the user's environment and the objects therein is typically created. The 3D model may then be augmented with particular types of data (e.g., descriptions), graphics (e.g., icons), etc., relating to particular locations and/or particular objects in the environment. When a user equipped with the appropriate AR gear moves through the mapped environment, the augmented portions can be rendered/displayed to the user, by overlaying digital information on the user's real-world view (e.g., a real-time camera view, or as a heads up display (HUD) through which the user observes the environment) without rendering/displaying the rest of the 3D model.

Conventionally, 3D models of this sort are manually constructed by human designers, and/or using a 3D scanner. Both of these approaches, however, can be very time- and labor-intensive for applications involving environments having complex layouts and/or a large number of objects. Moreover, any changes to the environment (e.g., as objects are moved or replaced/updated within the environment) can require that the entire modeling process be repeated, or other time- and labor-intensive procedures.

Current AR systems can suffer from other drawbacks as well. When used in relatively dense environments (e.g., environments having multiple objects that are in close proximity and/or have a large amount of information to display in the AR view), for example, AR systems may subject users to a vast amount of information that could easily lead to sensory overload, and/or the user may not easily perceive the context of all the information. Moreover, some objects may be obscured within the AR view. For example, objects may be located within an enclosure, or may reside at an inaccessible or inconvenient (e.g., distant) location.

SUMMARY

Techniques, systems, apparatuses, and methods for providing an augmented reality experience are disclosed herein. Said techniques, systems, apparatuses, and methods may apply to industrial process control systems, environments, and/or plants, for example, which may interchangeably be referred to herein as “process control” or “process” systems, environments, and/or plants. Typically, such systems and plants provide control, in a distributed manner, of one or more processes that operate to manufacture, refine, or otherwise transform raw physical materials to generate or produce products. In some embodiments, however, the techniques, systems, apparatuses, and methods described herein may be used in other types of environments, and/or used in a context other than augmented reality (e.g., in a virtual reality (VR) context).

Generally, process control environments can give rise to many of the various difficulties, discussed above in the “Background” section, that are associated with generating and using a conventional augmented reality (AR) system or platform. For example, such environments often contain a large number of diverse objects (e.g., tanks, pumps, valves, motors, transmitters, etc.) that are in close proximity and/or are associated with large amounts of information (e.g., sensor readings, diagnostic status, etc.). Moreover, those objects may be frequently moved or replaced.

An AR platform described herein may overcome or ameliorate some or all of these difficulties, and therefore may be well-suited for use in process control environments. With the AR platform, a three-dimensional (3D) model is generated by a user employing an AR mobile device. The AR mobile device may be an AR helmet, an AR head set, AR goggles, smart glasses, a smartphone, a tablet, or any other suitable type of mobile device that is capable of supporting location tracking (as discussed below) and can present an AR experience to a user.

The 3D model indicates 3D locations/positions of points of interest, within the process control environment, that correspond to different real-world objects (e.g., field devices, tanks, conveyors, controllers, switches, etc.). Objects that are added to the 3D model are referred to herein as “nodes” of the AR platform or system. As the term is used herein, an “object” (also referred to as a “real-world object”) may be any physical thing (e.g., a device, component, equipment, structure, etc.), portion of a thing (e.g., an element of a device or component, etc.), or combination of things (e.g., a group of related devices or components, etc.). In a process control environment, for example, an object may be a field device (e.g., valve, pump, sensor, etc.), piece of equipment (e.g., a conveyor, tank, etc.), process controller, switch, and so on.

In some implementations, when an AR application is launched on an AR mobile device (e.g., when specifically activated by the user, or upon device power-up), the user “checks in” or registers the AR mobile device at some reference or “landmark” location. For example, the user may scan a QR code, or another visual representation of a code/identifier, at the landmark location with a camera of the AR mobile device. The act of scanning the code may establish a starting location for the user/device (e.g., the coordinates {0,0,0} in an { x,y,z} space).

After registration, the user may begin to physically move through the process control environment with the AR mobile device. Suitable positioning technology (e.g., provided by the user's AR mobile device) may be used to track the user's movement through the process plant. Because GPS or GNSS units may not function well in many process plant environments and cannot provide orientation data or accurate elevation data (especially for process control environments that are indoors), other positioning and/or orientation technologies may be used. For example, the location of the AR mobile device relative to the landmark location, and the orientation of the AR mobile device (e.g., the direction of a field of view of a camera of the AR mobile device, which may correspond to the direction the user is facing), may be tracked using a fusion of inertial measurement unit (IMU) data (e.g., generated by accelerometers, gyroscopes, etc.) and camera image data. In one implementation, for example, the Visual-Inertial Odometry (VIO) technique developed by Qualcomm® is employed to track position and orientation.

When arriving at or near a real-world object that is to be added as a node, and while facing in the direction of the object (e.g., if wearing an AR helmet or goggles) or otherwise pointing the device camera at the object (e.g., if the device is a tablet or smartphone), the user may select an option to add a new node. For example, the AR mobile device may recognize the voice command “add node” when spoken by the user, or (e.g., if the device is a tablet or smartphone) the AR mobile device may allow the user to select an “Add Node” or similar option/control on a graphic user interface (GUI) of the AR mobile device display. The AR mobile device may then capture an image of the object, and process the image to estimate a distance between the AR mobile device and the object. Alternatively, other sensors (e.g., lidar, radar, etc.) may be used to determine the distance between the AR mobile device and the object. The AR mobile device may then determine the position of the object relative to the landmark location based on the current position and orientation of the AR mobile device, as well as the distance between the AR mobile device and the object. Alternatively, a remote server or other computing device/system may process image data captured by the AR mobile device to determine the object position relative to the landmark location.

The user may also specify the name or type of the new node (e.g., valve, pump, etc.) and/or other information (e.g., a model number or other identifier for the object, a short description of the object, etc.). The specified information may then be associated with the new node in a back-end database of the AR system. The back-end database may contain a library of nodes added by the user (and possibly other users as well), with associated 3D locations relative to the landmark location, to collectively establish a virtual, 3D “map” of objects/assets in the process control environment. The database may also store other node information, such as lists of related and/or connected nodes, for example.

After at least one object of interest in a particular process control environment has been mapped (i.e., added to the node library using an AR mobile device), any users who register their AR mobile devices at the landmark location (including the mapping user(s)) may take an augmented tour of the process control environment. When a user with a registered AR mobile device directs a field of view of a camera of the AR mobile device towards an area that includes a particular real-world object (e.g., if the user looks at the area while wearing an AR helmet or goggles), and if the object is already associated with a node in the node library, the AR mobile device may augment the real-world scene observed by the user with a node “marker” (e.g., text, an icon, a graphic, etc.) that appears to the user as if it were located at or near the coordinates of the object in the user's real-world view.

If the user selects a particular node (e.g., by focusing on the node marker, or issuing a voice command, etc.), the AR mobile device may make one or more “node experiences” available to the user. For example, one node experience may superimpose text (node name, description, etc.), tables, and/or graphics/icons on the real-world view of the user. Other node experiences may superimpose web content from a particular URL (e.g., an instructional or “help” video), or may superimpose visualizations of physical or logical connections to, and/or relationships with, other objects/nodes, for example. Still other node experiences may include retrieving a work order associated with the object/node, establishing a communication link between the user and an appropriate expert at a remote location, and so on. In some implementations, at least one node experience launches (or links to) one or more other software applications or systems, in the specific context of the object that is being observed by the user. For example, the AR mobile device may superimpose sensor data, status, and/or virtual controls for a selected object/node (e.g., a field device) in the field of view, where the data is received from (and user inputs to the controls are transmitted to) a different application.

The experiences available to a user for a given node, the type of content presented within a particular node experience, and/or, in some implementations, whether any augmented information at all is available to a particular user for a given node, may be determined based at least in part on the user's “role.” For example, a particular user may use the AR mobile device to select an “operator” role, a “maintainer” role, or an “engineer” role, or may be pre-assigned such a role.

A number of other features may be provided to users as well. In some implementations, for example, virtual “x-ray vision” may be provided to users by creating hyper-realistic or pseudo-realistic 3D model visualizations that, when superimposed on the real-world view of the user, may appear as if the user were seeing objects hidden within enclosures (e.g., within a cabinet) or behind barriers. The AR mobile device may also present the user with (and/or enable the user to select) certain node experiences associated with hidden objects, such as viewing status data or alerts associated with the hidden objects, issuing voice commands to control operation of the hidden objects, and so on.

As another example, the AR mobile device may superimpose an “avatar” of a limited-access and/or distant object/node on the user's real-world view. The object may be at the top of a high tower, for example, or in a toxic or high-voltage area, etc. As with the hidden objects, the user may be provided with certain node experiences that provide various kinds of interactions with the limited-access and/or distant object. In both the hidden object (“x-ray vision”) and the limited-access/distant object implementations/scenarios, users may be provided with an overall experience that is quite similar to having the object/node be right in front of, and plainly visible to, the user while the user interacts with the object.

Other types of functionality may also be supported by the AR platform. For example, current positions of users may trigger various alerts (e.g., a warning that the user is in a dangerous area) and/or or other displays of information. As another example, current and/or historical 3D positions of users within a process plant may be tracked/recorded for various purposes, such as ensuring employee evacuation in an emergency situation, ensuring that employees are not injured or otherwise in need of medical help, or monitoring training of certain employees.

The AR platform described above and further below may provide a number of advantages, depending on the specific implementation. By mapping only the relative 3D positions of certain objects, for example, the 3D model may be generated more easily and efficiently than with conventional means (e.g., using a 3D scanner to map the environment). Likewise, updates or reconfigurations of objects within the process control environment may be performed more quickly and easily. Moreover, by using the mapping process described herein, and by tracking the movement of AR mobile devices/users as described herein, the AR platform may determine when to provide augmented information to a user without requiring the expense and/or time of retrofitting, or otherwise equipping, objects with short-range communication technologies (e.g., Bluetooth or near-field communications (NFC) units), and without requiring time-consuming actions by users navigating the environment (e.g., scanning QR codes on objects, manual data entry of object identifiers, physically connecting to objects, etc.). Thus, conventional barriers to the deployment of an AR system, particularly in a process control environment, may be lessened or removed.

As another example, the AR platform may generally provide a marketplace in which third parties can offer new, customized types or classes of “node experiences” that correspond to different user interactions with objects/nodes, and/or can offer new content for existing node experiences. Instrumentation vendors or other entities may offer subscriptions to “help” information, or AR- or video-based work instructions for particular objects, for example. In some embodiments, a virtual “app store” may allow customers to license various applications, and/or subscribe to specific types of content that are desired for a customer's mobile workforce.

Furthermore, the features facilitating display/viewing of augmented information for obscured, distant and/or limited-access nodes may save a user's time (and therefore costs) and, in some implementations and/or scenarios, may improve worker safety by avoiding the need to visit dangerous areas.

Still further, the AR platform architecture may be highly flexible. The AR platform may facilitate the display of relevant information to users on a variety of different platforms, for example, such as smart helmets, smart goggles, smart phones, tablets, etc. The AR platform may also facilitate interactivity with a number of other software applications (e.g., process control software that is able to retrieve data indicative of control logic, device readings, etc.), and/or allow new experiences, content, or other functionality to be easily provided.

As noted above, certain implementations and/or features described herein need not be used in an AR system, and/or need not be used in a process control environment. For example, a user with a smartphone, tablet or other mobile device may be presented with “node experiences” based on the mapped 3D positions of objects within a plant and the user's current position and orientation, without necessarily providing those experiences as an AR display (e.g., using a virtual reality display or simply a GUI). As another example, the techniques described herein may be applied in environments other than process control environments, such as in office spaces, warehouses, hospitals, and so on.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting an example augmented reality (AR) system, which provides an AR platform that may support various methods, techniques, functions and/or features described herein.

FIG. 2 is a block diagram depicting components of an example process control environment in which the AR system of FIG. 1 may be utilized.

FIG. 3 depicts an example three-dimensional (3D) map of nodes in a process control environment.

FIGS. 4A through 4H depict example user interfaces that may be superimposed over a field of view provided by an AR mobile device.

FIGS. 5A and 5B depict example elements of a database that may be used in the AR platform.

FIG. 6 depicts an example embodiment and scenario in which a user of an AR mobile device is provided with virtual x-ray vision.

FIGS. 7A and 7B depict example user interfaces that may be superimposed over a field of view provided by an AR mobile device, to provide virtual proximity between a user and an object that is distant from the user or otherwise difficult to access.

FIG. 8 is a flow diagram of an example method for mapping a real-world process control environment using a mobile device.

FIG. 9 is a flow diagram of an example method for providing virtual enhanced vision to a user of an AR mobile device in a real-world process control environment.

FIG. 10 is a flow diagram of an example method for facilitating interaction between a user of an AR mobile device and a real-world object that may be in a distant or limited-access area of a process control environment.

DETAILED DESCRIPTION Example Augmented Reality System

FIG. 1 depicts an example augmented reality (AR) system 10 that may generally provide an AR platform for providing an AR experience in an environment (e.g., a process control environment). The AR system 10 includes an AR mobile device 12 of a user, and a back-end server 14 that may be communicatively coupled to the AR mobile device 12 via a network 16. The AR mobile device 12 may be any computing device having suitable processing and sensing capabilities and capable of being worn or otherwise carried by a user. For example, the AR mobile device 12 may be a device specifically configured for AR, such as an AR helmet (e.g., the Smart Helmet® developed by DAQRI®) or AR goggles. Alternatively, the AR mobile device 12 may be a device that also has non-AR applications (e.g., a tablet, smartphone, smart glasses, smart watch, etc.), but executes a software application that configures the device 12 to have AR capabilities. While FIG. 1 depicts only one AR mobile device 12, it is understood that a larger number of AR mobile devices, identical to or different than the AR mobile device 12, may be used in the AR system 10 in a similar manner.

The AR mobile device 12 is generally configured to provide an AR experience to the user, by augmenting the user's real-world view with contextual information (e.g., text, graphics, animations, etc.). The back-end server 14 generally supports the AR experience for the user, and for the users of other AR mobile devices, by managing data specifying how a user's real-world view should be augmented in particular situations, by receiving data from the AR mobile devices indicating the current state and/or environment of the AR device and/or user, and by providing data to the AR mobile devices as needed.

The network 16 includes one or more wireless networks, and possibly also one or more wired networks. In the example embodiment of FIG. 1, the AR platform of the AR system 10 utilizes a cloud-based architecture, and the network 16 includes the Internet. If the AR system 10 is utilized indoors, the network 16 may also include wireless networks that do not require any direct communication with a remote tower or base station, such as an IEEE 802.11 or “WiFi” network. In other embodiments, however, the network 16 includes a cellular network (e.g., LTE, GSM, etc.). As discussed further below, the AR system 10 may also include one or more other servers 18 that are communicatively coupled to the back-end server 14 and/or the AR mobile device 12, and collectively store and execute one or more applications 19.

As seen in the example embodiment of FIG. 1, the AR mobile device 12 may include a network interface 20, a display 22, a camera 24, an inertial measurement unit (IMU) 26, and a memory 30 storing an AR application 32. The network interface 20 is configured to enable communications with remote computing devices and systems, including the back-end server 14, using a wireless communication protocol of at least a portion of the network 16 (e.g., a WiFi or cellular network).

The display 22 may include hardware and associated firmware and/or software configured according to any suitable type of digital display technology. For example, the display 22 may use liquid crystal display (LCD) technology, light-emitting diode (LED) technology, organic light-emitting diode (OLED) technology, and so on. The display 22 may be generally transparent or translucent, or may be opaque. The structure or form factor of the display 22, and whether the display is transparent/translucent or opaque, generally depends on the type of the AR mobile device 12. If the AR mobile device 12 is a helmet, for example, the display 22 may have the form of a visor, and may be translucent such that any information displayed by the display 22 is superimposed on the direct, real-world view of the user (i.e., a “heads up display” or “HUD”). Conversely, if the AR mobile device 12 is a tablet or smartphone, the display 22 may have a conventional, rectangular form factor, and may only allow indirect views of the real-world (e.g., as captured by the camera 24).

The camera 24 may be any suitable type of optical sensor, such as a charge-coupled device (CCD) image sensor, for example. In alternative embodiments, the camera 24 is instead, or also includes, a different type of imaging device, such as a light detection and ranging (lidar) sensor or radar sensor, for example. The IMU 26 may include one or more sensors (e.g., accelerometers and/or gyroscopes) that generate data indicative of movement of the AR mobile device 12 in three dimensions. While not shown in FIG. 1, the AR mobile device may also have other components, such as microphone and/or speaker.

The memory 30 storing the AR application 32 may be any suitable type of persistent memory, such as a read-only memory (ROM) in solid state or hard drive form, for example. The AR application 32 generally coordinates the AR experience for the user of the AR mobile device 12, e.g., by generating the appropriate augmented information on the display 22 and communicating with the back-end server 14 as needed. FIG. 1 depicts a set of modules corresponding to example functions or features that may be performed or provided by the AR application 32, including a role identification module 40, a registration module 42, a positioning and orientation module 44, a node experience module 46, a node creation module 48, a vision enhancement module 50, and a position-based alert module 52. Each of the modules 40-52 will be discussed further below in connection with the operation of the AR system 10. In some embodiments, the AR application 32 includes fewer, more, and/or different modules than those shown in FIG. 1. For example, the AR application 32 may include a voice recognition module for recognizing user voice commands.

Also in the example embodiment of FIG. 1, the back-end server 14 includes a web services interface 60, an experience provisioning unit 62, a 3D model generation unit 64, a vision enhancement unit 66, an alert generation unit 68, and a user monitoring unit 70. Generally, the web services interface 60 may provide an object-oriented web-based interface to an AR database 72 that is coupled to (or included within) the back-end server 14. In some embodiments, the web services interface 60 provides an application programming interface (API) to remote devices, such as the AR mobile device 12.

The AR database 72 generally stores information defining a 3D map of a particular environment (e.g., by storing node identifiers, locations of the nodes within the 3D map relative to the landmark, and possibly other information associated with the nodes), and is discussed in further detail below (according to one particular embodiment) in connection with FIGS. 5A and 5B. The AR database 72 may be a single database or a collection of databases, and may be stored in a single physical memory, or distributed across multiple memories at one or more geographic locations. One, some or all of the elements/units 60 through 70 may be implemented as software instructions stored on persistent memory (e.g., ROM). In other embodiments, the back-end server 14 includes fewer, more, and/or different elements/units than those shown in FIG. 1.

In operation, a user who is wearing or otherwise carrying the AR mobile device 12 may cause the AR mobile device 12 to launch the AR application 32. The AR application 32 may be launched by manually selecting an icon on the display 22, issuing a voice command, or simply powering up the AR mobile device 12, for example.

In some embodiments, the role identification module 40 of the AR application 32 initially (e.g., upon launch) prompts the user to indicate a particular “role,” which may correspond to the user's job position, and/or may correspond to the particular task or tasks that the user is trying to accomplish by using the AR system 10, for example. In other embodiments, the user is first prompted to indicate his or her role at a later time (e.g., after registering at a landmark, as discussed below). One example user interface that the role identification module 40 may superimpose over a real-world view seen on or through the display 22 (e.g., over image frames captured by the camera 24, or the over the user's direct real-world view) is discussed below in connection with FIG. 4A. In an alternative embodiment, the role identification module 40 does not prompt the user to select a role, and instead determines a pre-assigned role of the user based on an identifier of the AR mobile device 12 and/or identification (e.g., name, employee number, etc.) entered or spoken by the user.

The selected or assigned user role may condition various aspects of the AR experience provided to the user, as discussed further below. Depending on the embodiment, the user role may be fixed once selected or assigned, or may be changed on the fly by a user as he or she moves through the environment. In some embodiments, the role identification module 40 is not included in the AR application 32, and no user roles are selected or assigned within the AR system 10.

Prior to mapping an environment, or prior to updating or exploring a previously mapped environment, the user may, in some embodiments, need to register the AR mobile device 12 at a “landmark,” the location of which is then used as a reference point for future movement of the AR mobile device 12 (and equivalently, the user). The same landmark location is also used as a reference point for the locations of any objects in the environment that have already been established (or will be established) as nodes of the 3D map, thereby enabling a determination of the position of the AR mobile device 12 relative to any mapped objects. The landmark location may represent {0,0,0} in an {x,y,z} coordinate system, for example, or other coordinate systems (e.g., polar coordinates) may be used.

To register the AR mobile device 12, the registration module 42 may process one or more images/frames captured by the camera 24. The landmark may be a QR code, or any other suitable type of image or text that is physically printed at the landmark location (e.g., on a wall or door near an entrance to an area within a process control plant), for example. In some embodiments, the registration module 42 or another portion of the AR application 32 may superimpose a reticle within the real-world view provided to the user (e.g., as discussed below in connection with FIG. 4E), to help the user focus on the QR code, image, etc. In some embodiments, a different technology is used to recognize the landmark, such as complementary Bluetooth or NFC communication units of the AR mobile device 12 and another device fixed at the landmark location.

In some embodiments, when the user registers the AR mobile device 24 at a particular landmark, the registration module 42 forwards data indicative of an identifier of the landmark (e.g., by transmitting a binary representation of the QR code, or transmitting the image of the QR code prior to decoding the image) to the back-end server 14 via the network 16 and web services interface 60. The back-end server 14 may then compare the landmark identifier to landmark identifiers (if any) stored in the AR database 72. If the identifier is not already stored, the back-end server 14 may return a failure message to the registration module via the web services interface 60 and the network 16 or, in some embodiments, may cause the AR database to create a new landmark identifier entry associated with a new 3D map. Conversely, if the landmark identifier already exists in the AR database 72, the back-end server 14 may make some or all of the corresponding 3D map (and associated data) available to the AR mobile device 12, and return a message indicating successful registration to the registration module 42 via the web services interface 60 and the network 16.

The AR database 72 may store a number of different landmark identifiers each associated with a different 3D map, with each map being associated with a different library of nodes. Multiple maps may be associated with a same environment (e.g., by adding different objects within the single environment as nodes of the different maps), and/or different maps may be associated with different environments (e.g., one map for a first area of a process control plant, another map for a second area of the plant, etc.).

In some embodiments, successful registration of the AR mobile device 12 at the landmark causes the positioning and orientation module 44 to set the location of the AR mobile device 12 equal to the landmark location (e.g., {0,0,0}). For greater precision, however, the registration module 42 may process the image of the landmark captured by the camera 24, using a depth sensing technique, to determine the distance between the AR mobile device 12 and the landmark. The positioning and orientation module 44 may then offset the starting position of the AR mobile device 12 from the known/reference position of the landmark based on both the determined distance from the landmark and the orientation of the AR mobile device 12 relative to the landmark. If the landmark is a QR code or other visual identifier, the relative orientation of the AR mobile device 12 may be assumed based on the direction the landmark is facing. Alternatively, the relative orientation may be determined from the captured image (e.g., by determining an angle of incidence of the camera view relative to the landmark, etc.).

Once registered, the user of the AR mobile device 12 may begin to move through the environment, with a real-world view (provided via the display 22) that is generally augmented by digital text, tables, graphics, animations, and/or other types of information associated with the 3D map corresponding to the landmark. To track the position and orientation of the user (i.e., of the AR mobile device 12), the positioning and orientation module 44 may access the IMU 26, the camera 24, and/or one or more other sensors of the AR mobile device 12 not shown in FIG. 1. In some embodiments, the positioning and orientation module 44 uses the collected sensor data to determine positions and orientations without relying on GPS, GNSS, WiFi positioning (e.g., trilateration), or any other positioning technologies that require a communication link between the AR mobile device 12 and other devices or systems. “Position” or “location” may refer to a particular set of coordinates in a 3D coordinate system (e.g., Cartesian or polar), and “orientation” may refer to a particular direction (e.g., in a 360 degree horizontal/azimuthal range, plus elevation or altitude). In some embodiments, “orientation” may further refer to the tilt of the AR mobile device 12, independent of the direction the device 12 is facing. Because only relative positions are tracked (e.g., in a “dead reckoning” sense), the positioning and orientation module 44 determines AR mobile device/user positions relative to the location of the landmark where registration occurred.

In some embodiments, the positioning and orientation module 44 processes a fusion of data from at least the camera 24 and IMU 26, to help overcome deficiencies associated with either type of sensor when used in isolation. For example, the positioning and orientation module 44 may utilize the Visual-Inertial Odometry (VIO) technology developed by Qualcomm® to track position and orientation of the AR mobile device 12. Such technology may help to improve accuracy, reduce “drift” in determined positions, and/or have other advantages.

Because the position and orientation of the camera 24 relative to the AR mobile device 12 itself is known, the AR application 32 can determine the field of view of the AR mobile device 12 (which may also, in some embodiments, correspond to the real-world view of the user) for any given position and orientation determined by the positioning and orientation module 44. Based on the determined position and orientation, and using the node locations stored in the AR database 72 for the 3D map, the AR application 32 may therefore determine which mapped objects are within the field of view at any given time. In some embodiments, an object may be considered to be “within the field of view” of a camera if the object is within the horizontal and vertical range/extent of the camera sensor (e.g., within certain azimuthal and vertical/altitude/elevation angles), regardless of the distance between the object and the AR mobile device capturing the images, and regardless of whether the object happens to be blocked by obstacles in the environment. For example, an object directly and immediately in front of the camera 24 may be considered “within the field of view” of the camera 24, even if the object is shielded by an enclosure, barrier, other object, etc. In other embodiments, an object is only considered to be “within the field of view” of the camera if the object is not obscured, i.e., while the camera is able to capture images of the object.

To determine the positions of mapped objects, the AR application 32 may periodically access node locations in the AR database via the network 16 and web services interface 60. For example, the AR application 32 may periodically request that the back-end server 14 provide location data for nodes within a threshold distance of the AR mobile device 12 (and/or within the field of view of the device 12, etc.), with the request indicating the current position (and/or orientation) of the AR mobile device 12. Alternatively, the AR application 32 may request that the back-end server 14 send all node locations (and possibly other information, such as node descriptions, etc.) for the 3D map that is associated with the landmark used for registration, e.g., at the time of registration. In still other embodiments, the back-end server 14 may automatically send all relevant node locations when the AR mobile device 12 successfully registers at the landmark.

The AR application 32 may determine that augmentation should be provided for one, more than one, or none of the mapped objects/nodes in the user's current field of view. To make this determination, the node experience module 46 may apply one or more criteria. In some embodiments, for example, the node experience module 46 may determine that augmentation is to be provided for all mapped objects in the user's current field of view, regardless of the distance between the object and the user and regardless of whether the object is blocked from the user's view by any obstacles. Alternatively, the node experience module 46 may determine that augmentation is not to be provided for mapped objects that are in the field of view but more than a threshold distance away from the user (e.g., as determined from the current user position determined by the positioning and orientation module 44, and from the corresponding node location stored in the AR database 72).

The node experience module 46 may also, or instead, determine that augmentation is not to be provided for mapped objects that are in the field of view of the AR mobile device 12 but blocked from sight. Whether mapped objects are obscured may be determined in different ways, depending on the embodiment. For example, a field in the AR database 72 may indicate whether a particular node corresponds to an object that would generally be obscured. For instance, for a component that is enclosed within a cabinet, the corresponding node have a field indicating the relationship between the component and the cabinet. In other embodiments, the AR application 32 and/or the back-end server 14 may perform a more complex analysis of node configurations, node types, and/or node sizes to determine whether, from the user's current perspective, a particular mapped object would likely be visible.

In some embodiments, to reduce the danger of sensory overload for the user, augmentation is not provided for certain types of mapped objects unless the user takes some specific action (beyond simply moving and/or re-orienting the AR mobile device 12). For example, the node experience module 46 may not provide augmentation for a large number of relatively small components within a cabinet, each corresponding to a different mapped object, unless the user selects an icon or other graphic representation of the cabinet, and/or selects an option to show cabinet contents, etc.

Further, in some embodiments, the node experience module 46 may determine whether augmentation is to be provided for a particular mapped object in the user's field of view based on the user's role, as determined by the role identification module 40. Thus, the node experience module 46 may query web services interface 60 specifically for nodes that are associated with both the landmark and the selected or assigned role. In a process control environment, for example, a power switch may be augmented for a user having a “maintainer” role, but not for a user having an “operator” role.

For objects that are to be augmented, the node experience module 46 may initially superimpose a node “marker,” such as text (e.g., a device identifier, status and/or description) and/or an icon or other graphic, etc., on an area of the display 22 that appears to the user as if it were located at (or near) the coordinates of the object in the user's real-world view. The marker may appear to be connected to the mapped object in the real-world view by a line rendered on the display 22, for example. In other embodiments, the marker is a circle or other shape rendered over the object, a rectangular outline roughly enclosing the object, or some other type of indicator.

If the user selects a particular node (e.g., by focusing a virtual reticle on the node marker, or by issuing a voice command, etc.), the node experience module 46 may make one or more “node experiences” available to the user. A “node experience”—in contrast to the more general “AR experience” of a properly equipped user moving through a mapped environment—refers to a particular type or types of user interaction with the object/node. The node experience module 46 may provide the user with the option of selecting specific node experiences by superimposing a menu or other interactive display on the real-world view, for example, and/or by being configured to recognize voice commands from the user. A user may select menu options in a manner similar to selecting node markers (e.g., focusing a virtual reticle on the option, voice command, etc.), or in another suitable manner.

When a specific node experience is selected, the node experience module 46 may forward the selection to the web services interface 60 via the network 16. In response, the experience provisioning unit 62 may retrieve data (e.g., text, graphics, etc.) associated with the selected node and the selected experience from the AR database 72 (and/or other locations, such as server(s) 18), and send the retrieved data back to the AR mobile device 12 via the web services interface 60 to enable the node experience module 46 to augment the user's real-world view accordingly.

A node experience may be relatively simple, or complex. The node marker itself may be considered a default “node experience,” for example. As other examples, the node experience module 46 may superimpose other text and/or tables (i.e., information associated with the corresponding object) on the user's real world view (via display 22), a simple graphic or icon of the object, a hyper-realistic or pseudo-realistic 3D model of the object, an image of the object, an animation including the object (e.g., a rotating 3D model of the object), and so on.

Node experiences may also, or instead, include other types of interactivity. For example, the node experience module 46 may superimpose a link (e.g., a URL) to a video that provides a tutorial on the object and/or its operation within the environment (e.g., within a particular process control routine), to a work order that involves the object, or to a remote expert. Alternatively, or in addition, the user may issue voice commands for some or all of these node experiences. In an embodiment where content such as a video or work order is selected or called, the node experience module 46 may superimpose the content on the user's real-world view. If a remote expert or other person is selected or called, the node experience module 46 may cause the network interface 20, or another suitable network interface, to establish a communication link with the person (e.g., via the network 16), and in some embodiments may superimpose a still image or video of the person until the communication ends.

Other node experiences may list and/or graphically depict particular types of relationships between the selected object/node and other objects/nodes. For one node experience, for example, the node experience module 46 may superimpose a list of objects/nodes related to the selected object/node (e.g., parent and/or child objects/nodes) over the user's real-world view. A “relationship” may be defined in any way desired, and may be manually set by a user when adding a new node, or set in another suitable manner. For example, some relationships may refer to whether an object is a component of another object, and/or itself includes a number of components. A valve may correspond to a node that is a parent to a group of nodes each corresponding to components of the valve, for instance.

The node experience module 46 may determine relationships by querying the experience provisioning unit 62 via web services interface 60, with the experience provisioning unit 62 retrieving identifiers of the related nodes from the AR database 72 and providing an indication of those nodes to the node experience module 46. By not showing, by default, node markers and/or node experiences for all of the individual valve components (e.g., unless a node or a particular option is specifically selected by the user), the user may be spared from receiving an overwhelming amount of visual information all at once.

Some kinds of relationships may be graphically depicted to the user. For example, the node experience module 46 may provide a graphical depiction of a physical or logical connection between the object corresponding to the selected node and one or more other objects corresponding to other nodes. The node experience module 46 may determine connections by querying the experience provisioning unit 62 via web services interface 60, with the experience provisioning unit 62 retrieving identifiers of the connected nodes from the AR database 72 and providing an indication of those nodes to the node experience module 46. The node experience module 46 may then generate a display depicting lines connected the appropriate objects, and superimpose the lines on the user's real-world view. One example of such a node experience is provided in FIG. 4H, discussed below.

The connections and/or other relationships shown may also vary based on the user's selected or assigned role. In a process control environment, for example, an “operator” may be shown a line from a sensor/transmitter device to a tank, with the line indicating that the sensor/transmitter measures the pressure in the tank. Conversely, an “engineer” may instead (or additionally) be shown a line from the sensor/transmitter to another device that receives the sensor transmissions, and a “maintainer” may instead (or additionally) be shown a line from the sensor/transmitter to a power source for the device (e.g., so the maintainer can easily find where to shut down power before maintaining, repairing or replacing the device).

In some embodiments, the experience provisioning unit 62 utilizes data and/or functionality from other server(s) 18 and/or application(s) 19 in order to provide one or more node experiences, and/or one or more of the application(s) 19 may be launched in response to data sent from the experience provisioning unit 62. Some examples of such embodiments, in a process control environment, are discussed below in connection with FIG. 2.

As noted above, the node experience module 46 may determine whether to augment the user's real-world view of a particular mapped object based on the user's selected or assigned role (e.g., operator, maintainer, etc.). In addition, or alternatively, the types of node experiences, and/or the content or interactivity provided by a particular experience, may vary based on the user role. For example, a user having a role of “maintainer,” and having a pump in his or her real-world view, may be presented with a node experience showing a scheduled maintenance reminder for the pump, while a user having a role of “operator” or “engineer” may instead be presented with information relating to logical connections of the pump within a process control routine. The maintainer may be shown an alert if the scheduled maintenance is overdue, while the operator or engineer may only be shown an alert in other scenarios (e.g., if the pump fails).

The node creation module 48 supports the addition of new nodes within the 3D map corresponding to the landmark used to register the AR mobile device 12. In some embodiments, any user can add new nodes to a 3D map. In other embodiments, only certain user roles, and/or only certain AR devices, can be used to add new nodes. To add a new node, a user may direct the field of view of the AR mobile device 12 (e.g., a reticle centered within the field of view) to a real-world object that is to be mapped, and select an option to add the object as a new node.

This may be accomplished in different ways, depending on the embodiment. For example, the user may select a superimposed menu item (e.g., a virtual “Add Node” button), or issue a voice command, and the node creation module 48 may superimpose a reticle on the user's real-world view in response. While aiming the reticle at the object, the user may activate another control (e.g., a virtual “Confirm” button) or issue a second voice command. In response, the node creation module 48 may determine a position of the object, and prompt the user to enter a node name and/or description. The node creation module 48 may then send the position, the entered or spoken name, etc., to the web services interface 60 via the network 16, and the 3D model generation unit 64 may add at least the position and a node identifier (e.g., the node name entered or spoken by the user) to the AR database 72.

To determine the position of the object being mapped, the node creation module 48 may utilize the current position of the AR mobile device 12 (as determined by the position and orientation module 44), and offset that position based on both the distance between the AR mobile device 12 and the object, and the orientation of the AR mobile device 12. This may be accomplished in a manner similar to determining the initial 3D position of the AR mobile device 12 when registering at the landmark, as described above. For example, the node creation module 48 may process the image of the object captured by the camera 24, using a depth sensing technique, to determine the distance between the AR mobile device 12 and the object. The positioning and orientation module 44 may then offset the object position from the position of the AR mobile device 12 based on both the determined distance and the orientation of the AR mobile device 12 (e.g., based on the distance and the direction that the field of view of the AR mobile device 12 was facing when the image of the object was captured).

In some embodiments, the node creation module 48 may also be used to update/modify existing nodes. For example, a menu that is provided by the node experience module 46 may include an option for updating node information. If selected, the node creation module 48 may superimpose one or more menus or other user interfaces on the user's real-world view, to enable the user to change information pertaining to the node (e.g., node name, node description, etc.). Any changes may be sent to web services interface 60 via the network 16, and the 3D model generation unit 64 may update the AR database 72 accordingly.

In some embodiments, the AR application 32 configures the AR mobile device 12 to enhance the virtual vision of the user, beyond the augmentation features described above. For example, for certain types of nodes, the vision enhancement module 50 may determine when a mapped object is within an area captured by the user's current field of view (e.g., as discussed above for the node experience module 46), but obscured by one or more other objects, and provide virtual “x-ray vision” to the user. The virtual x-ray vision may only be provided if one or more other criteria is/are established (e.g., if the vision enhancement module 50 determines that the hidden object(s) is/are within a threshold distance of the AR mobile device 12), or may be provided regardless of any other criteria.

In one such embodiment, the AR database 72 includes, for each of at least some of the node entries, a flag or other visibility indicator indicating that the node is likely hidden from any user's view. This visibility indicator may have been generated automatically based on a known relation of objects (e.g., if the 3D model generation unit 64 accesses a control system to learn that the object corresponding to the node is positioned within a cabinet), or may have been manually set by a user (e.g., when adding the node, via a user interface that the node creation module 48 superimposes on the real-world view of the user). When a particular mapped object is within the user's field of view, the vision enhancement module 50 may query the vision enhancement unit 66 of the back-end server 14, via the network 16 and web services interface 60, and the vision enhancement unit 66 may in turn access the AR database 72 to retrieve the relevant visibility indicator. The vision enhancement unit 66 may then use web services interface 60 to send the visibility indicator, or other data indicating whether the object is obscured, to the vision enhancement module 50.

Alternatively, the vision enhancement module 50 and/or vision enhancement unit 66 may make the visibility determination in other ways. For example, a particular mapped object or set of objects may be inside a cabinet that is marked with a model number, QR code, or other visual indicator. The vision enhancement module 50 may process an image of the visual indicator that is captured by the camera 24 to determine an identifier (e.g., node identifier) of the cabinet, and send the identifier to the vision enhancement unit 66 via web services interface 60. The vision enhancement unit 66 may then use the identifier to determine which mapped objects (e.g., field devices, I/O cards, etc.) are within the cabinet, and send back data indicating that the objects that are within the cabinet are obscured.

To provide the effect of virtual x-ray vision for a given object, the vision enhancement module 50 may retrieve a hyper-realistic or pseudo-realistic 2D or 3D model of the object, or a digital image or video of the object, and superimpose that model, image, or video over the object (or near the object) in the user's field of view. Either by default, or in response to a user selection of the 2D or 3D model, or voice command, etc., the node experience module 46 may also provide visual menu options or voice command recognition to enable the user to select various experiences for the node, as described above. Thus, the user may interact with the hidden object in a manner that appears and “feels” very similar to interacting with the real-world object while it is directly in his or her field of view.

The vision enhancement module 50 may also, or instead, enhance a user's virtual vision in other ways. If an object is in a limited-access and/or dangerous area (e.g., in a very high location, a barricaded location, a high-voltage or toxic area, etc.), and/or far away from the user, for example, the vision enhancement module 50 may enable the user to retrieve an “avatar” that represents the object into his or her field of view. The avatar may be the same as the 2D or 3D model, image, video, etc., described above for the x-ray vision example, or may differ in some respects. Indeed, in some embodiments, virtual x-ray vision is simply one of multiple use cases for summoning an avatar of a real-world object.

An avatar may be summoned in different ways, depending on the embodiment and/or the scenario. In some embodiments, the vision enhancement module 50 first superimposes a visual indicator on the user's real-world view, if certain criteria are satisfied, with the visual indicator giving some indication of the corresponding object's location relative to the user's real-world view. For example, the visual indicator may be presented if both (1) the AR mobile device 12 is within some threshold distance of the object, and (2) the node is flagged as a limited-access object. The AR database 72 may store data indicating such a status, for example (e.g., based on a manual user input when the node was added by a user), or the status may be inferred (e.g., if the vision enhancement unit 66 determines the object is in a region that the back-end server 14 has flagged as a “danger” region, or if the vision enhancement module 50 or vision enhancement unit 66 determines the position of the object is at least a threshold distance from the AR mobile device 12 in the z-direction and thus at a very different elevation, etc.). The visual indicator may include an arrow pointing in the direction of the object, a line leading to the object, or some other indication of location. One example of a visual indicator is discussed below in connection with FIG. 7A. If the user selects the indicator or takes another suitable action (e.g., in some embodiments, if the user changes his or her field of view to include the object), the vision enhancement module 50 may superimpose the avatar on the user's real-world view.

In other embodiments, the indicator of the object's location includes the avatar itself (e.g., with an arrow/pointer to the object location overlying or near the avatar). In still other embodiments and/or scenarios, the vision enhancement module 50 superimposes the avatar on the user's field of view without presenting any visual indicator of the object's location. For example, the vision enhancement module 50 may present the avatar to the user in response to the user requesting or searching for the corresponding object (e.g., by issuing a voice command or manually entering data), or in response to the user selecting a node marker for a relatively distant object (e.g., more than some threshold distance away), etc. In one such embodiment, the avatar does not instantly appear at full size. For instance, the vision enhancement module 50 may create a visual effect in which the avatar appears to the user as if it moves from the object location (e.g., far ahead of the user) to a position just in front of the user. The avatar may expand in size to simulate the effect of drawing nearer to the user, for example.

The node experience module 46 may automatically provide a particular node experience for the object to the user (in addition to showing the object's avatar), and/or may enable the user to select one or more node experiences after the avatar is first presented (e.g., by issuing a voice command or selecting menu options). For example, any one or more of the node experiences discussed above may be provided. One example of an experience that may be associated with an avatar is discussed below in connection with FIG. 7B.

In some embodiments, the AR application 32 configures the AR mobile device 12 to generate alerts based on the user's current position and/or based on current circumstances in particular areas (e.g., certain regions of a process plant being associated with a warning). The alert generation unit 68 may periodically or continuously determine whether the current position of the AR mobile device 12 is in an area subject to an alert or warning, e.g., by comparing positions reported by the positioning and orientation module 44 (via web services interface 60) to the boundaries of one or more geo-fenced areas. If the user/device is in an area associated with an alert, the alert generation unit 68 may send an indicator of the alert to the position-based alert module 52 via web services interface 60, and the position-based alert module 52 may superimpose an indication of the alert (e.g., text and/or a graphic) on the user's real-world view, cause some other visual effect (e.g., a flashing red light or tint encompassing the entire real-world view), and/or provide an audio alert to the user (via a speaker of the AR mobile device 12, not shown in FIG. 1). Alternatively, or additionally, the alert generation unit 68 may send an alert indicator based on the proximity of the AR mobile device 12 to a particular mapped object (e.g., if the object is malfunctioning and needs maintenance, or should be avoided, etc.). The alert generation unit 68 may also condition the delivery of alerts on the user's selected or assigned role.

In some embodiments, the back-end server 14 may monitor the 3D locations of AR mobile devices (and thus, users) in the mapped environment. To this end, the user monitoring unit 70 may record current and/or historical positions of users who have registered their AR mobile devices at a landmark, based on data received from the positioning and orientation module 44 via web services interface 60.

User location monitoring may be used for various purposes, depending on the embodiment and/or the need. For example, the user monitoring unit 70 may depict user locations on a display or terminal coupled to the back-end server 14 (and not shown in FIG. 1), and an operator of the display or terminal may account for employee locations in the event of an emergency, or simply monitor users in more typical conditions to determine whether any employees are in need of medical aid. Employee health may also be monitored using other data, such as biometric data collected by one or more sensors of the AR mobile device 12 (e.g., to detect pulse, blood pressure, temperature, etc.). As further examples, employee/user locations may be added to employee training logs, used by managers or human resources personnel to monitor compliance with protocols, and so on. In still other embodiments and/or scenarios, 3D locations of certain non-human mobile assets may be tracked within the mapped environment. For example, a unit of the back-end server 14 may monitor 3D locations of mobile reactors, carts, field service trucks, and/or other objects for various purposes.

It is understood that FIG. 1 and the above description represent only some potential embodiments, and that others are possible as well. For example, the AR platform may not use a cloud-based architecture or web-based services. As another example, the functionality of some or all of the units 62 through 68 of the back-end server 14, and/or the AR database 72 itself, may instead be partially or wholly incorporated into the AR mobile device 12. As yet another example, node markers and/or node experiences may be provided in a non-AR context, e.g., in a virtual reality (VR) context, or in connection with non-AR, non-VR graphical user interfaces (GUIs).

Moreover, the AR platform may provide still other features not discussed above. For example, users of AR mobile devices may add field notes (e.g., using voice commands) that are stored in association with various nodes/objects in the AR database 72, and/or may initiate new work orders associated with various nodes/objects, and so on.

Example Process Control Environment

FIG. 2 is a block diagram of an example process control environment 100 in which the AR system 10 of FIG. 1 may be utilized. The process control environment 100 (which is also interchangeably referred to herein as a process control system 100 or process plant 100) includes one or more process controllers that receive signals indicative of process measurements made by field devices, process this information to implement a control routine, and generate control signals that are sent over wired and/or wireless process control communication links or networks to other field devices to control the operation of a process in the plant 100. Typically, at least one field device performs a physical function (e.g., opening or closing a valve, causing a conveyor to move materials, increasing or decreasing a temperature, taking a measurement, sensing a condition, etc.) to control the operation of a process. Some types of field devices communicate with controllers by using I/O devices. Process controllers, field devices, and I/O devices may be wired or wireless, and any number and combination of wired and wireless process controllers, field devices, and I/O devices may be included in the process plant environment or system 100.

For example, FIG. 2 illustrates a process controller 111 that is communicatively connected to wired field devices 115-122 via input/output (I/O) cards 126 and 128. The process controller 111 includes a processor 130, a memory 132, and one or more process control routines 138 that are discussed in further detail below. The controller 111 is also communicatively connected to wireless field devices 140-146 via a process control communication network or backbone 110 and a wireless gateway 135. The backbone 110 may include one or more wired and/or wireless communication links, and may be implemented using any suitable communication protocol such as, for example, an Ethernet protocol. In some configurations (not shown in FIG. 2), the controller 111 may be communicatively connected to the wireless gateway 135 using one or more communications networks other than the backbone 110, such as by using any number of other wired or wireless communication links that support one or more communication protocols, e.g., an IEEE 802.11-compliant wireless local area network protocol, a mobile communication protocol (e.g., WiMAX, LTE, etc.), Bluetooth®, HART®, WirelessHART®, Profibus, FOUNDATION® Fieldbus, etc.

The controller 111 (which, by way of example, may be the DeltaV™ controller sold by Emerson Process Management) may operate to implement a batch process or a continuous process using at least some of the field devices 115-122 and 140-146. In an embodiment, in addition to being communicatively connected to the backbone 110, the controller 111 is also communicatively connected to at least some of the field devices 115-122 and 140-146 using any desired hardware and software associated with, for example, standard 4-20 mA devices, I/O cards 126, 128, and/or any suitable smart communication protocol such as the FOUNDATION® Fieldbus protocol, the HART® protocol, the WirelessHART® protocol, etc. In FIG. 2, the controller 111, the field devices 115-122 and the I/O cards 126, 128 are wired devices, and the field devices 140-146 are wireless field devices. Of course, the wired field devices 115-122 and wireless field devices 140-146 could conform to any other desired standard(s) or protocols, such as any suitable wired or wireless protocols, and including any suitable standards or protocols developed in the future.

The processor 130 of process controller 111 implements or oversees the one or more process control routines or modules 138, which may be stored in the memory 132. To this end, the processor 130 is configured to communicate with the field devices 115-122 and 140-146, and with other nodes that are communicatively connected to the controller 111. It should be noted that any control routines or modules described herein may have parts thereof implemented or executed by different controllers or other devices if so desired. Likewise, the control modules 138 to be implemented within the process control system 100 may take any form, including software, firmware, hardware, etc. Control routines may be implemented in any desired software format, such as using object oriented programming, ladder logic, sequential function charts, function block diagrams, or using any other software programming language or design paradigm. The memory 132, on which some or all of the control modules 138 may be stored, may be any suitable type of memory or memories, such as random access memory (RAM) and/or read only memory (ROM). Moreover, the control modules 138 may be hard-coded into, for example, one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. Thus, the controller 111 may be configured in any desired manner to implement a control strategy or control routine/module.

The controller 111 implements a control strategy using what are commonly referred to as function blocks, where each function block is an object or other part (e.g., a subroutine) of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process control system 100. Control-based function blocks typically perform one of an input function, such as that associated with a transmitter, a sensor or other process parameter measurement device; a control function, such as that associated with a control routine that performs PID, fuzzy logic, etc. control; or an output function which controls the operation of some device, such as a valve or conveyor motor, to perform some physical function within the process control system 100. Of course, hybrid and other types of function blocks exist. Function blocks may be stored in and executed by the controller 111, which is typically the case when these function blocks are used for, or are associated with, standard 4-20 mA devices and certain types of smart field devices (e.g., HART® devices), or may be stored in and implemented by the field devices themselves, which can be the case with FOUNDATION® Fieldbus devices. The one or more control modules 138 in the controller 111 may implement one or more control loops which are performed by executing one or more of the function blocks.

The wired field devices 115-122 may be any type or types of devices, such as sensors, valves, conveyor motors, transmitters, positioners, etc., while the I/O cards 126 and 128 may be any types of I/O devices conforming to a suitable communication or controller protocol. For example, the field devices 115-118 may be standard 4-20 mA devices or HART® devices that communicate over analog lines (or combined analog and digital lines) to the I/O card 126, while the field devices 119-122 may be smart devices, such as FOUNDATION® Fieldbus field devices, that communicate over a digital bus to the I/O card 128 using a FOUNDATION® Fieldbus communications protocol. In some embodiments, though, at least some of the wired field devices 115-122, and/or at least one of the I/O cards 126, 128, additionally or alternatively communicate(s) with the controller 111 using the backbone 110 and a suitable control system protocol (e.g., Profibus, DeviceNet, Foundation Fieldbus, ControlNet, Modbus, HART, etc.).

In FIG. 2, the wireless field devices 140-146 communicate via a wireless process control communication network 170 using a wireless protocol, such as the WirelessHART® protocol. Such wireless field devices 140-146 may directly communicate with one or more other devices or nodes of the wireless network 170 that are also configured to communicate wirelessly. To communicate with other nodes that are not configured to communicate wirelessly, the wireless field devices 140-146 may utilize a wireless gateway 135 connected to the backbone 110 or another process control communications network. The wireless gateway 135 provides access, from the backbone 110, to various wireless devices 140-158 of the wireless communications network 170. In particular, the wireless gateway 135 provides communicative coupling between the wireless devices 140-158, the wired devices 115-122, and/or other nodes or devices of the process control plant 100.

Similar to the wired field devices 115-122, the wireless field devices 140-146 of the wireless network 170 perform physical control functions within the process plant 100, e.g., opening or closing valves, taking measurements of process parameters, etc. The wireless field devices 140-146, however, are configured to communicate using the wireless protocol of the network 170. As such, the wireless field devices 140-146, the wireless gateway 135, and other wireless nodes 152-158 of the wireless network 170 may be producers and consumers of wireless communication packets.

In some configurations of the process plant 100, the wireless network 170 includes non-wireless devices. For example, in FIG. 2, a field device 148 may be a legacy 4-20 mA device and a field device 150 may be a wired HART® device. To communicate within the network 170, the field devices 148 and 150 are connected to the wireless communications network 170 via a respective one of wireless adaptors 152A, 152B. The wireless adaptors 152A, 152B support a wireless protocol, such as WirelessHART, and may also support one or more other communication protocols such as Foundation® Fieldbus, PROFIBUS, DeviceNet, etc. Additionally, in some configurations, the wireless network 170 includes one or more network access points 155A, 155B, which may be separate physical devices in wired communication with the wireless gateway 135, or may be integrated within the wireless gateway 135. The wireless network 170 may also include one or more routers 158 to forward packets from between wireless devices within the wireless communications network 170. The wireless devices 140-146 and 152-158 may communicate with each other, and with the wireless gateway 135, over wireless links 160 of the wireless communications network 170, and/or via the backbone 110.

In FIG. 2, the process control system 100 includes one or more operator workstations 171 that are communicatively connected to the backbone 110. Via the operator workstation(s) 171, human operators may monitor run-time operations of the process plant 100, as well as take any diagnostic, corrective, maintenance, and/or other actions that may be required. At least some of the operator workstations 171 may be located at various, protected areas in or near the plant 100, e.g., in a back-end environment of the plant 100, and in some situations, at least some of the operator workstations 171 may be remotely located (but nonetheless in communicative connection with the plant 100). Operator workstation(s) 171 may be wired or wireless computing devices.

The example process control system 100 is further illustrated in FIG. 2 as including one or more configuration applications 172A and one or more configuration databases 172B, each of which is also communicatively connected to the backbone 110. Various instances of the configuration application(s) 172A may execute on one or more computing devices (not shown in FIG. 2) to enable users to create or change process control modules and download these modules via the backbone 110 to the process controller 111 and/or other process controllers, as well as enable users to create or change operator interfaces via which an operator is able to view data and change data settings within process control routines. The configuration database(s) 172B store(s) the configured modules and/or operator interfaces. Generally, the configuration application(s) 172A and configuration database(s) 172B may be centralized and have a unitary logical appearance to the process control system 100 (although multiple instances of a configuration application 172A may execute simultaneously within the process control system 100), and the configuration database(s) 172B may be stored in a single physical data storage device or across multiple data storage devices. The configuration application(s) 172A, the configuration database(s) 172B, and user interfaces thereto (not shown in FIG. 2) collectively form a configuration or development system 172 for creating/configuring control and/or display modules. Typically, but not necessarily, the user interfaces for the configuration system 172 are different than the operator workstations 171, with the user interfaces for the configuration system 172 instead being utilized by configuration and development engineers irrespective of whether the plant 100 is operating in real-time, and with the operator workstations 171 being utilized by operators during real-time (or “run-time”) operations of the process plant 100.

The example process control system 100 also includes one or more data historian application(s) 173A and one or more data historian database(s) 173B, each of which is communicatively connected to the backbone 110. The data historian application(s) 173A operate(s) to collect some or all of the data provided across the backbone 110, and to store the data in the data historian database(s) 173B for long term storage. Similar to the configuration application(s) 172A and configuration database(s) 172B, the data historian application(s) 173A and data historian database(s) 173B may be centralized and have a unitary logical appearance to the process control system 100 (although multiple instances of a data historian application 173A may execute simultaneously within the process control system 100), and the data historian database(s) 173B may be stored in a single physical data storage device or across multiple data storage devices. The data historian application(s) 173A, the data historian database(s) 173B, and user interfaces thereto (not shown in FIG. 2) collectively form a data historian system 173.

In some configurations, the process control system 100 includes one or more other wireless access points 174 that communicate with other devices using other wireless protocols, such as IEEE 802.11-compliant wireless local area network protocols, mobile communication protocols such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution) or other ITU-R (International Telecommunication Union Radiocommunication Sector) compatible protocols, short-wavelength radio communications such as near field communications (NFC) or Bluetooth, and/or other wireless communication protocols. Typically, such wireless access point(s) 174 allow handheld or other portable computing devices (e.g., user interface devices 175) to communicate over a respective wireless process control communication network that is different from the wireless network 170 and that supports a different wireless protocol than the wireless network 170. For example, a wireless or portable user interface device 175 may be a mobile workstation or diagnostic test equipment that is utilized by an operator within the process plant 100 (e.g., an instance of one of the operator workstations 171). In some scenarios, in addition to portable computing devices, one or more process control devices (e.g., controller 111, field devices 115-122, wireless devices 135, 140-158, etc.) also communicate using the wireless protocol supported by the wireless access point(s) 174.

It is noted that although FIG. 2 only illustrates a single process controller 111, and a particular number of field devices 115-122 and 140-146, wireless gateways 35, wireless adaptors 152, access points 155, routers 1158, and wireless process control communications networks 170 included in the example process plant 100, this is only an illustrative and non-limiting embodiment. For example, any number of controllers 111 may be included in the process control plant or system 100, and any of the controllers 111 may communicate with any number of wired or wireless devices and networks 115-122, 140-146, 135, 152, 155, 158 and 170 to control a process in the plant 100.

Referring now back to FIG. 1, the objects mapped using AR mobile devices (e.g., AR mobile device 12) may include some or all of the controller 111, the devices 115-122 and 140-158, the I/O cards 126, 128, the wireless gateway 135, and/or other devices and/or pieces of equipment in the plant 100, such that their 3D positions within the plant 100 (and possibly their relationships to each other, their avatars, etc.) are stored in the AR database 72. In some embodiments, the back-end server 14 may be communicatively coupled to the backbone 110, and the other server(s) 18 may include, or be coupled to, the operator workstation(s) 171, configuration system 172, data historian system 173, and/or other computing devices or systems of the process control environment 100.

The application(s) 19 run by the server(s) 18 may include one or more DeltaV™ applications, diagnostics and maintenance applications, and/or other applications or software-based systems. The application(s) 19 may thus support node experiences that display run-time status and/or measurement data of field devices, provide run-time controls for field devices, display diagnostics/maintenance information for machinery, and so on. As just one example, HART® and/or Fieldbus information associated with various devices may be presented to the user of the AR mobile device 12. The experience provisioning unit 62 may launch and/or interface with the appropriate application(s) 19 (e.g., via the backbone 110) to gather the required display data, which is then forwarded to the node experience module 46. The experience provisioning unit 62 may also, or instead, forward any user inputs that were received from the node experience module 46 to the controller 111 to cause the appropriate field devices to be controlled accordingly, etc.

Example 3D Map

It should be understood from the description of FIG. 1 above that the 3D “map” of the AR system 10 need not be a full model of the environment, and may include only 3D locations of nodes within that environment. A highly simplified example 3D map 200, containing only four objects/nodes, is shown in FIG. 3. In FIG. 3, the z axis corresponds to elevation (e.g., above ground level). As discussed above, a landmark location 202 may provide a reference point for all other locations (e.g., node and user/AR device locations) within the environment.

In the example map 200, a first location 204 of a first object/node is slightly above (elevation-wise) the landmark location 202 at the offset {x1,y1,z1}, second and third locations 206, 208 of second and third objects/nodes are a bit higher still at the offsets {x2,y2,z2} and {x3,y3,z3}, respectively, and a third location 210 of a third object/node is higher still at the offset {x4,y4,z4}. Of course, in some scenarios, offsets in the x, y and/or z directions may be negative for certain objects/nodes.

Within the map 200, a location 220 at {x5,y5,z5} corresponds to a current location of an AR mobile device, such as the AR mobile device 12 of FIG. 1. FIG. 3 also depicts, in dashed lines, a field of view 222 of the AR mobile device, corresponding to a particular orientation of the device. The field of view 222 may be determined by the positioning and orientation module 44 of FIG. 1, for example, using sensor data from the IMU 26 (and possibly image data from the camera 26, e.g., with VIO technology) and a known azimuthal range/angle of the camera 26. While not illustrated in FIG. 3, the positioning and orientation module 44 may also know the extent of the field of view 222 in the z direction, e.g., such that the field of view 222 has a cone-like shape rather than assuming infinite coverage in the z-direction.

In this example scenario, the objects at locations 206 and 208 are within the device's/user's current field of view 222, while the objects at locations 204 and 210 are not. The experience provisioning unit 62 of FIG. 1 may make this determination, for example, based on the node positions (as stored in AR database 72), the location 220 and orientation of the AR mobile device (as determined by the positioning and orientation module 44 and forwarded via web services interface 60), and the known or estimated characteristics of the field of view for the camera 24. Based on the determination of which objects/nodes are within the field of view 222, the experience provisioning unit 62 may send data to the AR mobile device 12 indicating that a node marker (and/or a particular node experience) is to be presented only for the objects at locations 206 and 208. The node experience module 46 may process that data, and in response superimpose node markers and/or other information at or near points on the display 22 that correspond to the locations 206 and 208.

Example AR User Interfaces

A set of example user interfaces that may be superimposed on an AR display (e.g., the display 22 of the AR mobile device 12 of FIG. 1) will now be described in connection with FIGS. 4A through 4H. For ease of explanation, reference will also be made to the AR system 10 of FIG. 1, although the user interfaces shown may instead be used in other systems. For user interfaces where user selections may be made, the selection may be made by the user looking directly at a specific menu option (e.g., if the user interfaces have a fixed position relative to the environment, rather than a fixed position relative to the center of the display 22). In other embodiments, the selection may be made by the user issuing an appropriate voice command, entering data on a keyboard or touch screen, or in another suitable manner.

Referring first to FIG. 4A, a user interface 200 enables the user to select a particular “role,” as discussed above in connection with FIG. 1. The user interface 200 may be displayed to the user upon launch of the AR application 32, or at another suitable time. The AR application 32 may know the available roles a priori, or may be informed of the available roles by querying the back-end server 14 via web services interface 60. Once a role is selected, the role identification module 40 may send data indicative of the role to the back-end server 14 via web services interface 60. The experience provisioning unit 62, alert generation unit 68, and/or other components of the back-end server 14 may then utilize the selected role to determine appropriate nodes to augment, appropriate types of experiences and/or content to provide for particular nodes, and so on, as discussed above.

FIG. 4B depicts a user interface 220 that may act as a node marker for each of some or all objects within the user's current field of view (subject to any other criteria, such as proximity or user role). The example user interface 220 includes an icon (circled “X”) and descriptor (“StatusWord”) that indicate a status of the object/node, a node name (e.g., a device identifier within a process control plant, such as “ESD-3,” etc.), a short description of the node (e.g., “emergency shutdown switch,” etc.), and a vertical line leading from those pieces of information to a solid-fill circle at that bottom of the user interface 220. The solid-fill circle (or other indicator) may be placed on the {x,y,z} location of the corresponding object within the user's real-world view, e.g., at the real-world {x,y,z} location that the user (or another user) focused upon when adding the node to the 3D map. The text and line may rotate as needed to stay aligned with the vertical axis of the AR mobile device 12 and user, or may always align to the z-axis, for example.

The status icon and descriptor may indicate whether some action should be taken with respect to the object, and/or whether some danger exists with respect to the object. For example, the circled “X” shown in FIG. 4B may correspond to a status of “Critical,” the “!” in a triangle may correspond to a status of “Warning,” the “i” in a diamond may correspond to a status of “Advisory,” and no icon may correspond to a status of “Normal.” While FIG. 4B shows a range of possible status icons, it is understood that the user interface 220 only includes, for this particular embodiment and/or scenario, the circled “X” icon. The status depicted for a particular object/node, and the meaning of that status, may vary depending on the user's role.

The node marker (i.e., in FIG. 4B, the text, line, and solid-fill circle) of the user interface 220 may scale in size with distance from the AR mobile device 12, such that nearer objects have larger node markers and more distant objects have smaller node markers. In some embodiments, the user interface 220 includes more information, by way of additional text, additional graphics, and/or color-coding (e.g., red text and line for “Critical” status, green text and line for “Normal” status, etc.), for example.

FIG. 4C depicts a user interface 240 that may appear after a user role is selected at user interface 200, or at another suitable time. The “+” icon in the user interface 240 may be selected by the user to add a new node to the 3D map, as discussed above in connection with FIG. 1. The helmet icon may be selected by the user to select a different role, and the third icon may be selected by the user to manage certain settings, as discussed below. The rectangular box in the user interface 240 may display system messages to the user. For example, the message box may be used to display alerts generated by the alert generation unit 68 and/or the position-based alert module 52.

FIG. 4D depicts a user interface 260 that may appear if the user selects the settings icon in the user interface 240. As seen in FIG. 4D, the user interface 260 enables the user to change the name or identifier of the AR mobile device 12, the landmark identifier, and a name or IP address of the back-end server 14. Some or all of these values may be used by the AR mobile device 12 when making web service calls to web services interface 60, for example.

FIG. 4E depicts a simple user interface 280 that may appear if the user selects the “+” (add node) icon in the user interface 240. In this example, the user interface 280 is simply a reticle (e.g., in the center of the user's display 22) that the user may center on any location in the real-world environment simply by looking around (e.g., if the AR mobile device 12 is an AR helmet or goggles, or smart glasses), or by otherwise aiming the camera 24 of the AR mobile device 12 (e.g., if a tablet or smartphone). The node creation module 48 of the AR application 32 may require that the user confirm when the reticle is appropriately placed (e.g., by issuing a voice command), or may assume appropriate placement if the field of view of the camera 24 does not change substantially for some threshold period of time, etc.

FIG. 4F depicts a user interface 300 that may appear after the user has positioned the reticle of the user interface 280, and after the positioning and orientation module 44 has determined the necessary position and/or orientation information for placing the new object/node (e.g., the position of the AR mobile device 12, the orientation of the device 12, and the distance from the device 12 to the object). The example user interface 300 includes a text box for the user to enter a node name and/or node description. Alternatively, some or all of this information may be provided by voice command (e.g., if the user selects the microphone icon). In other embodiments, the node name and/or description may be determined by processing an image of a portion of the object using optical character recognition (OCR) technology. For example, the user may direct the camera 24 towards a tag or label that is affixed to the object and includes a serial number, model number, or other identifier. The identifier may then be sent to the back-end server 14 via web services interface 60 and cross-referenced with information stored at the back-end server 14, or stored in another system or database (e.g., one of the other server(s) 18), to determine the node name and/or description.

FIG. 4G depicts a user interface 320 that may appear for a specific object/node when the user has selected that object/node (e.g., by selecting the node marker of user interface 220). The user interface 320 may be generated by the node experience module 46, based on data indicative of available experiences for the node that is provided by the experience provisioning unit 62 of the back-end server 14, for example. The example user interface 320 includes the node name and description that were shown on the node marker in the user interface 220, as well as two rectangular areas. The solid-fill circle at the bottom of the user interface 320 may remain at the same position on the object (within the real-world view) that it was at in the user interface 220. A first, “working” area, shown as a blank rectangle in FIG. 4G, may show additional information pertaining to the selected object/node, such as status information for the object, detailed alert information for the object, and so on (e.g., depending upon the type of node experience being provided and/or the user's role).

The user may select the desired type of node experience from the second area, listing those that are available for the node (and possibly, for the user's role). As seen in FIG. 4G, in this example, available node experiences include “More Info” (e.g., to provide additional types of text-based information in the working area), “Connections” (e.g., to show physical or logical connections to other objects/nodes, as discussed below in connection with FIG. 4H), “Info Link” (e.g., to show, in the working area, information from a “help” document, instructional video, or other web page at a particular URL), “Child Objects” (e.g., to show, in the working area, relationships with other objects/nodes that are related as “children” of the selected object/node), “Process Values” (e.g., to show, in the working area, control process values obtained from one of the other server(s) 18 and application(s) 19), and “Work Order” (e.g., to show, in the working area, text of a work order associated with the selected object/node).

FIG. 4H depicts a user interface 340 that may appear when the user has selected the “Connections” icon in the user interface 320. For the user interface 340, the node experience module 46 renders a line between the {x,y,z} position of the currently-selected object/node, and the {x,y,z} position of an object/node to which the currently-selected object/node is physically and/or logically connected (e.g., as discussed above in connection with FIG. 1). The solid-fill circle at the bottom of the user interface 340 may be at the former position, while the solid-fill circle at the top of the user interface 340 may be at the latter position. Of course, the relative positions of the solid-fill circles may change depending upon the scenario (e.g., the circle for the selected object/node may appear higher in the real-world view than the circle for the connected object/node).

In the embodiment of FIG. 4H, the node experience module 46 renders the connecting line in three segments: a first segment (starting at the currently-selected object/node) indicating the distance and direction along the y-axis, a second segment (starting at the end of the first segment) indicating the distance and direction along the x-axis, and a third segment (starting at the end of the second segment) indicating the distance and direction along the z-axis and ending at the connected object/node. The line segments may be color-coded, coded by line format (dashed, solid, etc.), and/or coded in other ways to provide additional information (e.g., a red line to indicate a communications connection that is currently inoperative). In other embodiments, the connection may be depicted in a different manner, such as a single line segment between the objects/nodes (e.g., with the line getting wider or narrower to portray distance from the user). In various different embodiments, connections to multiple different objects/nodes can be shown in the user interface 340, or the user may need to select each individual connection for which a visualization is desired.

Example AR Database

FIGS. 5A and 5B collectively depict a database structure 400 that may be utilized by the AR database 72 of FIG. 1 (e.g., when used in the process control environment 100 of FIG. 2). In the database structure 400, each box represents a table that may be stored in the AR database 72, with the top line of each box being the table name (e.g., “Nodes,” “NodeStatus,” etc.). The tables are linked using primary keys, each of which is denoted in FIGS. 5A and 5B by a key icon and the letters “PK.”

The database structure 400 enables efficient cross-referencing of data items, and permits user and system updates without breaking existing links or requiring extensive updates. For example, using the “Node ID” primary key permits the user to change the “Node Name” for an existing node without the need to update other, related tables. The “GetOPCDA” table in FIG. 5B may correspond to the “Process Values” node experience described above in connection with FIG. 4G.

Example Enhanced Virtual Vision

FIGS. 6 and 7 relate to embodiments in which an AR platform (e.g., provided by the AR system 10 of FIG. 1) provides features that enhance the “virtual vision” of the user. FIG. 6 depicts a specific scenario in which a “virtual x-ray vision” feature (discussed above in connection with FIG. 1) is used to “see” into a closed cabinet within a process control environment (e.g., within the process control environment 100 of FIG. 2), while FIGS. 7A and 7B depict a specific scenario in which an “avatar” (also discussed above in connection with FIG. 1) is provided for a sensor/transmitter device that is in a limited access (e.g., hard-to-reach or dangerous) area of the process control environment, and/or is distant from the user's current location.

Referring first to the example of FIG. 6, a closed (and possibly locked) cabinet 500 may contain a number of interior components (not seen in FIG. 6), such as I/O cards, circuit breakers, etc. When any of the criteria discussed above in connection with FIG. 1 are satisfied (e.g., the interior components being within a field of view of the AR mobile device 12 and within a threshold distance, and/or the cabinet 500 being selected by the user, etc.), and if the cabinet 500 is determined to contain obscured objects/nodes (also as discussed above, e.g., based on a known relationship between the cabinet and interior components, and/or by scanning a QR code, etc.), the vision enhancement module 50 of FIG. 1 may superimpose a user interface 520 on the user's real-world view.

The user interface 520 includes a depiction 522 of the interior components. The depiction 522 may be an image of the actual components within the cabinet 500, in their actual arrangement relative to each other. In other embodiments, the depiction 522 includes hyper- or pseudo-realistic graphical representations of the components (e.g., 3D models, 2D models, etc.), either individually or in a manner that depicts their relative arrangement within the cabinet 500. In either case, the depiction 522 may provide the user with an AR experience similar to the experience he or she would have if viewing the actual interior components.

The user interface 520 may be superimposed directly over the cabinet 500 in the user's real-world view, and scaled appropriately so as to align the depiction 522 over the actual positions of the hidden interior components. Alternatively, the user interface 520 may be offset from the cabinet 500 in the user's real-world view, possibly connected by a line or some other means.

The depiction 522 may or may not include node markers (e.g., similar to the user interface 220 of FIG. 4B) for individual ones of the internal components, to the extent that those components have previously been mapped. Moreover, the user interface 520 may enable the user to select various node experiences by selecting such a node marker, by selecting the depiction 522 itself, or by issuing an appropriate voice command. The depiction 522 or user interface 520 may also include a control (e.g., an “X” in one corner) that the user can select to dismiss the depiction 522 from his or her view, or a suitable voice command may be used.

Referring now to FIG. 7A, an direction indicator 550 includes a depiction of a particular object (here, a sensor/transmitter device) along with an arrow showing the general direction of the object relative to the user's real-world view. The vision enhancement module 50 of FIG. 1 may superimpose the direction indicator 550 over the user's real-world view in response to any of the conditions described above (in connection with FIG. 1) with respect to avatars of distant and/or limited-access objects, for example. The depiction of the device in the example direction indicator 550 is a realistic model or image, though of course other formats are also possible (e.g., an outline, animation, video, etc.).

If the user selects the direction indictor 550, the vision enhancement module 50 may superimpose an “avatar” 560 on the user's real-world view, as shown in FIG. 7B. While the avatar 560 shown in FIG. 7B is identical to the depiction of the object in the direction indicator 550, in other embodiments, the avatar 560 is more detailed and/or realistic than the depiction (if any) in the direction indicator 550. Similar to the depiction 522 of FIG. 6, the avatar 560 may provide the user with an AR experience similar to what he or she would have if viewing the actual object (here, sensor/transmitter device) in close proximity. Indeed, as noted above, the virtual x-ray vision feature of FIG. 6 may simply be a special case of the vision enhancement shown in FIG. 7B, with the depiction 522 of FIG. 6 being a collection of avatars for the various components enclosed within the cabinet 510.

If the user selects the avatar 560 or issues an appropriate voice command, the vision enhancement module 50 may superimpose a user interface 570 near to the avatar 560 within the user's real-world view. Alternatively, the user interface 570 may be presented with the avatar 560 by default, without requiring any user selection of the avatar 560 or any voice command. The example user interface 570 of FIG. 7B corresponds to a node experience that provides process values (here, sensor readings), and permits user control of the device (here, by initiating a calibration process). To enable this node experience, the experience provisioning unit 62 of FIG. 1 may communicate with one or more of the application(s) 19 run by the other server(s) 18, as discussed above. For example, the experience provisioning unit 62 may cause a process control application to launch, or interface with an executing process control application using an API, etc.

Example 3D Mapping Method

FIG. 8 depicts an example method 600 for mapping a real-world process control environment (e.g., process control environment 100 of FIG. 2) using a mobile device. The method 600 may be performed using the AR mobile device 12 of FIG. 1, for example, or another suitable mobile device. In some embodiments, a mobile device without AR capability may be used.

At block 602, the mobile device is registered at a reference or “landmark” location in the process control environment. The registration may include using a camera of the mobile device (e.g., camera 24 of FIG. 1) to scan a visual representation of a code (e.g., a QR code or other image) located at the reference location. The code may be on a wall (e.g., on a plate or poster), for example.

At block 604, at least an IMU of the mobile device (e.g., the IMU 26 of FIG. 1) is used to track 3D positions of the mobile device relative to the reference location, and to track orientations of the mobile device, as the mobile device is moved through the process control environment by the user. Block 604 may continue indefinitely (e.g., simultaneously with blocks 606 through 610), until the user ends the AR experience (e.g., by powering down the mobile device, or closing an application running on the mobile device, etc.). The tracking at block 604 may also use the mobile device camera. For example, VIO technology may be used to track the position and orientation of the mobile device.

At block 606, a user input, indicating that a new node is to be added to a 3D map of the process control environment, is detected at the mobile device. The user input may be a user voice command (e.g., “Add Node”), or a user selection of a menu option (e.g., by focusing the mobile device camera on a particular location, or entering data on a keyboard or touch screen), for example.

At block 608, a 3D position of a real-world object (relative to the reference location) is determined, or caused to be determined, based at least on a tracked 3D position of the mobile device and a tracked orientation of the mobile device. In one embodiment, block 608 includes capturing an image of a real-world object using the mobile device's camera (e.g., at the time the user input was entered, or shortly thereafter). The distance between the mobile device and the object may then be determined from the image, at least by processing the camera image using a depth sensing technique. The 3D position may then be determined, or caused to be determined, based on the tracked 3D position and orientation of the mobile device, as well as the determined distance.

In some embodiments, the 3D position of the object is directly determined at block 608 by the device, system, etc., that performs the method 600. In other embodiments, the device, system, etc., that performs the method 600 causes another device, system, etc., to determine the 3D position of the object, e.g., by making a request via a web services interface (e.g., web services interface 60 of FIG. 1).

At block 610, a node database or library is caused to add the new node to the 3D map, at least by causing the 3D position of the object to be stored in association with the new node. Block 610 may include using a web services interface to cause a remote server (e.g., back-end server 14 of FIG. 1) to store at least the 3D position of the new node in the node database (e.g., AR database 72 of FIG. 1), for example.

The method 600 may include one or more blocks not shown in FIG. 8. For example, the method 600 may include a block in which another user input (e.g., voice command, keyboard entry, etc.) is received at the mobile device, with the user input indicating an identifier (e.g., name) and/or description of the new node. In such an embodiment, block 610 may further include causing the identifier and/or description of the new node to be stored in association with the new node, within the node database.

As another example, the method 600 may include additional blocks corresponding to later operations of a different mobile device (or later operations by the same mobile device performing the blocks 602 through 610), which navigates an area of the process control environment after the new node has been added to the 3D map. In a first block, for example, a second mobile device (e.g., AR mobile device 12 or a similar device) may be registered at the reference location. Thereafter, 3D positions of the second mobile device (relative to the reference location) and orientation of the second mobile device may be tracked using at least an IMU of the second mobile device (e.g., using VIO technology). A triggering condition may then be detected, by determining (e.g., based on a tracked orientation of the second mobile device) that the object is within an area inside a field of view of a camera of the second mobile device, and/or determining (e.g., based on a tracked position of the second mobile device), that the physical object is proximate to the second mobile device, for example. In response to detecting the triggering condition, digital information associated with the new node may be superimposed on a real-world view seen on or through a display of the second mobile device (e.g., a node marker, or in accordance with any node experience discussed above).

Example Method for Providing Virtual X-Ray Vision

FIG. 9 depicts an example method 620 for providing virtual enhanced vision (e.g., virtual “x-ray vision”) to a user of an AR mobile device in a real-world process control environment (e.g., the process control environment 100 of FIG. 2). The method 620 may be performed by one or more processors of a computing system or device, such as the back-end server 14 of FIG. 1, and/or an AR mobile device such as the AR mobile device 12 of FIG. 1, for example.

At block 622, it is determined that a particular node (“first node”), associated with a map of the process control environment, corresponds to a particular real-world object (“first object”) that is currently within the field of view of a camera of the AR mobile device (e.g., camera 24 of FIG. 1). The first object may be any device shown or described in connection with FIG. 2, for example, or any other physical thing that is at least partially opaque. In some embodiments, the first object is an enclosure, such as a cabinet configured to contain a number of smaller devices or components.

In some embodiments, block 622 includes detecting a current orientation of the AR mobile device, and determining, based on the current orientation of the AR mobile device, and further based on the position of the first node as indicated by the map, that the first object is currently within the field of view of the camera. Block 622 may also include determining that the first object is within some threshold distance of the AR mobile device (e.g., 10 meters, 50 meters, etc.) based on the current position of the AR mobile device and the first node position.

At block 624, a specific relationship, between the first node and one or more other nodes that are also associated with the map, is determined. The relationship indicates (explicitly or implicitly) that one or more other real-world objects, corresponding to the one or more other nodes, is/are at least partially obscured by the first object. For example, a node database (e.g., AR database 72, or a portion thereof) may store data indicating that the first node corresponds to a cabinet or other enclosure that contains the object(s) corresponding to the other node(s) (e.g., controllers, I/O cards, switches, etc.), and block 624 may include accessing the node database directly (e.g., in a local memory) or via another computing system. In some embodiments, the first object is marked with a QR code or other visual code, and block 624 includes both scanning the code to determine a node identifier, and using the node identifier to determine the relationship (e.g., by using the identifier as a key to a database).

At block 626, one or more digital models or digital images are retrieved from memory (e.g., a local or remote persistent memory), with the model(s) or image(s) depicting the object(s) that is/are at least partially obscured by the first object. For example, one or more hyper-realistic or pseudo-realistic 3D models, 2D models, animated models, digital images, or digital video of the object(s) may be retrieved from the memory.

At block 628, a display of the AR mobile device (e.g., the display 22 of FIG. 1) is caused to present the retrieved model(s) or image(s) to the user while the first object is still in the field of view of the camera. For example, the model(s) or image(s) may be superimposed on a real-world view that is presented to the user on the display or seen by the user through the display. Block 628 may include transmitting at least some of the display content, and/or transmitting display instructions, to the AR mobile device (e.g., via web services interface 60 of FIG. 1), for example.

The method 620 may include one or more blocks not shown in FIG. 9. For example, the method 620 may include a block in which one or more node experiences are presented to the user for the obscured objects (e.g., initially with the model(s) or image(s), or in response to a further action, such as a user selection of the model or image of a particular obscured object).

Example Method for Visualizing Limited-Access Objects

FIG. 10 depicts an example method 640 for facilitating interaction between a user of an AR mobile device and a real-world object (“first object”) that may be in a limited-access (e.g., dangerous, barricaded, etc.) area of a process control environment (e.g., the process control environment 100 of FIG. 2). The method 640 may be performed by one or more processors of a computing system or device, such as the back-end server 14 of FIG. 1, and/or an AR mobile device such as the AR mobile device 12 of FIG. 1, for example.

At block 642, a display of the AR mobile device (e.g., the display 22 of FIG. 1) is caused, as the user moves through the process control environment, to superimpose digital information on portions of the environment that are within the field of view of a camera of the AR mobile device (e.g., the camera 24 of FIG. 1). The superimposed information is associated with nodes in a map (e.g., 3D map) of the process control environment, with the nodes corresponding to other real-world objects in the environment. Block 642 may include transmitting at least some of the display content, and/or transmitting display instructions, to the AR mobile device (e.g., via web services interface 60 of FIG. 1), for example.

At block 644, the display of the AR mobile device is caused to indicate a direction to the first object while the first object is not within the field of view of the camera. The indication may comprise text, an arrow, a line, and/or an animation, for example. Similar to block 642, block 644 may include transmitting at least some of the display content, and/or transmitting display instructions, to the AR mobile device (e.g., via web services interface 60 of FIG. 1), for example.

At block 646, after detecting a user input that was made via the AR mobile device and indicates selection of the first object (e.g., a voice command requesting a user interface for the first object), the display is caused to superimpose, on a portion of the process control environment that is currently within the field of view but does not include the first object, a digital model or image of the first object (i.e., an “avatar” of the first object), as well as a user interface for the first object. The avatar may be a hyper-realistic or pseudo-realistic 3D model, 2D model, animated model, digital image, or digital video of the object, for example. The user interface may include one or more virtual controls enabling user control of the first object (e.g., to calibrate the first object, set operational parameters of the first object, etc.), and/or one or more displays presenting information associated with status (e.g., diagnostic status, maintenance status, operational status, etc.), settings, and/or outputs (e.g., sensor readings, etc.) of the first object. In some embodiments, the user interface is not presented at the same time as the avatar, and instead appears (along with the avatar) in response to a user selection of the avatar or voice command.

In some embodiments, the indication of direction at block 644 occurs before detecting the user input indicating selection of the first object (i.e., the sequence shown in FIG. 10). In some such embodiments, the direction indicator (e.g., an arrow pointing towards an off-display area containing the first object) may be generated and displayed in response to detecting (1) that the first object is within a threshold distance of the AR mobile device, and (2) that the first object is not currently within the field of view of the camera. Other suitable triggers or criteria for the direction indicator are also possible. For example, the indicator may only be provided to users having a certain user role that is relevant to the first object.

In other embodiments, the indication of direction instead occurs after detecting the user input that had indicated the selection of the first object. For example, the user may issue a voice command requesting that a user interface be retrieved for the first object (e.g., a user “search” for the first object), after which the direction indicator (and possibly avatar) is superimposed on the user's real-world view.

The digital model or image, whether displayed with the direction indicator and/or at a subsequent stage, may be retrieved from a database using a web services interface (e.g., from the AR database 72 of FIG. 1 using the web services interface 60).

General Considerations

When implemented in software, any of the applications and functions described herein may be stored as instructions in any tangible, non-transitory computer readable memory such as on a magnetic disk, a laser disk, solid state memory device, molecular memory storage device, or other storage medium, in a RAM or ROM of a computer or processor, etc. Although the example systems disclosed herein are disclosed as including, among other components, software and/or firmware executed on hardware, it should be noted that such systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components could be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Accordingly, while the example systems described herein are described as being implemented in software executed on a processor of one or more computer devices, persons of ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such systems.

While the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, it will be apparent to those of ordinary skill in the art that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention. 

What is claimed:
 1. A method of mapping and navigating a real-world process control environment using mobile devices, the method comprising: registering a first mobile device at a reference location in the process control environment; tracking, using at least a first inertial measurement unit of the first mobile device, (i) three-dimensional (3D) positions of the first mobile device relative to the reference location, and (ii) orientations of the first mobile device; detecting, at the first mobile device, a user input indicating that a new node is to be added to a 3D map of the process control environment; determining a 3D position of a real-world object relative to the reference location, or causing the 3D position of the real-world object to be determined, based at least on (i) a tracked 3D position of the first mobile device and (ii) a tracked orientation of the first mobile device, at least by capturing an image of the real-world object using a first camera of the first mobile device, determining a distance between the first mobile device and the real-world object, at least by processing the image of the real-world object using a depth sensing technique, and determining the 3D position of the real-world object, or causing the 3D position of the real-world object to be determined, based at least on (i) the tracked 3D position of the first mobile device, (ii) the distance between the first mobile device and the real-world object, and (iii) the tracked orientation of the first mobile device; causing a node database to add the new node to the 3D map of the process control environment, at least by causing the 3D position of the real-world object to be stored in association with the new node; tracking, using at least a second inertial measurement unit of a second mobile device, (i) 3D positions of the second mobile device, and (ii) orientations of the second mobile device; detecting a triggering condition, by one or both of (i) determining, based on a tracked orientation of the second mobile device, that the real-world object is within an area inside a field of view of a second camera of the second mobile device, and (ii) determining, based on a tracked position of the second mobile device, that the real-world object is proximate to the second mobile device; and in response to detecting the triggering condition, causing digital information associated with the new node to be superimposed on a real-world view presented via a display of the second mobile device.
 2. The method of claim 1, further comprising: registering the second mobile device at the reference location, wherein tracking 3D positions of the second mobile device includes tracking the 3D positions of the second mobile device relative to the reference location.
 3. The method of claim 1, wherein registering the first mobile device at the reference location includes: using the first camera to scan a visual representation of a code, the visual representation being located at the reference location.
 4. The method of claim 1, wherein detecting a user input indicating that a new node is to be added to the 3D map includes: detecting a voice command, a keyboard entry, or a touch screen entry.
 5. The method of claim 1, further comprising: receiving, at the first mobile device, a user input indicating an identifier, and/or a description, of the new node, wherein causing the node database to add the new node to the 3D map of the process control environment further includes causing the identifier and/or the description of the new node to be stored in association with the new node.
 6. The method of claim 1, wherein the first mobile device and the second mobile device are augmented reality (AR) mobile devices that superimpose digital information on real-world views presented via displays of the AR mobile devices.
 7. A system for mapping a real-world process control environment, the system comprising: a server; a first mobile device comprising a first camera and a first inertial measurement unit; and a second mobile device comprising a second camera and a second inertial measurement unit, wherein the first mobile device is configured to register at a reference location in the process control environment, track, using at least the first inertial measurement unit, (i) three-dimensional (3D) positions of the first mobile device relative to the reference location, and (ii) orientations of the first mobile device, and detect a user input indicating that a new node is to be added to a 3D map of the process control environment, wherein either the first mobile device or the server is configured to determine a 3D position of a real-world object relative to the reference location based on (i) a tracked 3D position of the first mobile device and (ii) a tracked orientation of the first mobile device, at least by determining a distance between the first mobile device and the real-world object, at least by processing an image of the real-world object using a depth sensing technique, the image being captured by the first camera, and determining the 3D position of the real-world object, or causing the 3D position of the real-world object to be determined, based at least on (i) the tracked 3D position of the first mobile device, (ii) the distance between the first mobile device and the real-world object, and (iii) the tracked orientation of the first mobile device, wherein the server is configured to add the new node to the 3D map of the process control environment to a node database that stores the 3D position of the real-world object in association with the new node, and wherein the second mobile device is configured to track, using at least the second inertial measurement unit, (i) 3D positions of the second mobile device, and (ii) orientations of the second mobile device, detect a triggering condition, by one or both of (i) determining, based on a tracked orientation of the second mobile device, that the real-world object is within an area inside a field of view of the second camera, and (ii) determining, based on a tracked position of the second mobile device, that the real-world object is proximate to the second mobile device, and in response to detecting the triggering condition, cause digital information associated with the new node to be superimposed on a real-world view presented via a display of the second mobile device.
 8. The system of claim 7, wherein: the first mobile device is configured to register at the reference location at least by using the first camera to scan a visual representation of a code, the visual representation being located at the reference location.
 9. The system of claim 7, wherein the first mobile device is configured to detect a user input indicating that a new node is to be added to the 3D map at least by: detecting a voice command, a keyboard entry, or a touch screen entry.
 10. The system of claim 7, wherein the first mobile device and the second mobile device are augmented reality (AR) mobile devices that superimpose digital information on real-world views presented via displays of the AR mobile devices. 